Oscilloscope panel capture and implementation

ABSTRACT

A method and apparatus for saving the operational settings of an instrument. The method comprises the steps of: initiating the saving operation, initializing, by each software object, of any software object below it, initializing the internal variables belonging to the software objects, and saving the results to a file. The file is modular, is human readable text and is a computer program. The internal variable is designated in the file by a hierarchical path and is designated in the file by a hierarchical address. The computer program in an industry standard programming language such as Visual Basic Script.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application Ser. No. 60/249,482 filed Nov. 17, 2000, the entire contents thereof being incorporated herein by reference.

BACKGROUND OF THE INVENTION

The present invention relates generally to a method and apparatus for processing waveform data acquired by an oscilloscope using a streaming architecture.

A Digital Oscilloscope is a complex instrument for measuring electrical signals. It is composed of many electronic hardware modules and many software modules that cooperate together in capturing, processing, displaying and storing information that characterizes the signals of interest to an operator. There are several groups of requirements that need to be addressed when creating instruments that are easy to set up and use, despite the inherent complexity of the task.

SUMMARY OF THE INVENTION

The internal variables, what can be called “control variables” are a very common and central aspect of any instrument control software. The instrument (oscilloscope or related instrument) has a “state” at any moment in time for example a certain number of components are configured and the processing components each have their state (e.g. the FFT component may have selected a certain “window”, and a timing parameter a certain threshold or hysteresis). If the instrument is to ever be restored to that state, there needs be a means to store or record this overall state.

At any one time, the operator configures the instrument to perform the measuring task at hand by selecting appropriate value or setting for each of many hundred operating properties, that govern, to name only a few for example, the speed of signal capture, the number of measurement points, the sensitivity of input circuits, the type and quality of signal enhancement procedures applied in real time, the style of display of data, the parameters to be evaluated on the captured signals in real time. Each of these properties is embodied in a software entity that we name a Cvar (control variable). The set of current values of all Cvars in the instrument constitutes the control state of the instrument. You use the Cvars to control the state of the scope: the timebase, the vertical channel sensitivity, the trigger conditions, the Math and Parameter settings, the display landscapes, and tens and hundreds of other details.

Operators using the instrument need efficient means for manipulating and viewing the current values and the sets of possible values of Cvars. Manipulators include physical buttons and knobs on the instrument's front panel, virtual buttons and knobs on the instrument's screen, and Remote or Automation commands issued by computer programs that may run on separate computers connected to the instrument over a network. Operators also need efficient means for saving entire sets of Cvars in the form of computer files, for the purpose of repeating the same type of measurements at different times and/or in different places. This allows the instrument to remember the settings for the user. The user can also store, on the instrument's storage medium such as a hard disk, any number of ‘setups’ that the user can recall at a later date. These setup files can even be exchanged between different scope models that belong to the same instrument family, for example using the email. Each different model will try to accept the settings from a different model, and adapt them the best it can to approximate the state saved on the other instrument.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the invention, reference is made to the following description and accompanying drawings, in which:

FIG. 1 is a graphical depiction of a conceptualization of the operation of an oscilloscope constructed in accordance with the invention;

FIG. 2 graphically depicts a Cvar;

FIG. 3 graphically depicts a CvarBag;

FIG. 4 graphically depicts the concept of Widgets;

FIG. 5 shows the relationship of the Cvars and the other components;

FIG. 6 shows a sequences of events that takes place when the operator changes a setting on the instrument;

FIG. 7 depicts in more detail the inner operation of a Cvar;

FIG. 8 depicts the initialization of Cvars, panel capture and retrieval;

FIG. 9 is a flow chart showing the initialization of Cvars;

FIG. 10 depicts the screen for using the invention; and

FIG. 11 shows a graphic representation of a Cvar.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The preferred embodiments of the apparatus and method according to the present invention will be described with reference to the accompanying drawings.

In accordance with the invention, an oscilloscope design is provided that is completely “modular”, whereby the elements composing the oscilloscope software are completely specified in terms of interface, and are sufficiently independent in construction that they can be installed and removed at run-time, (e.g. without stopping the process which can be considered the oscilloscope application software). This is in contrast to existing products that include software that must be wholly replaced (in it's entirety) in order to change any small attribute of the software. This inventive approach offers commercial advantage because is shortens the overall logistics of releasing new software features, fundamental to the product or fundamental to a particular application of the product. As such, a special feature can be added after a customer has taken delivery and has the instrument (oscilloscope) in operation, after the fact, without the requirement to return or for that matter even stop using the instrument. This is of value to both the customer and the manufacturer.

Further, the modular design permits “unit testing” to further advance the quality of the overall product by permitting each individual component of the software to be tested in a standard “test harness”. Each component is provided with a standardized interface especially conceived to permit isolated testing. This forward looking, quality conscious aspect of the design assures final deployments of the product(s) are not hampered by the inability to localize faulty components.

FIG. 1 depicts a conceptualized notion of how the oscilloscope constructed in accordance with the invention operates. The flow of data is shown from left to right and control sequences provided by a user, either automated or manual, are shown from top down. As is shown in FIG. 1, a plurality of analog acquisition signals C₁ are acquired by the oscilloscope of the invention. These acquisition signals are that are in turn controlled by an acquisition control module 112 acquired in accordance with various provided probes and other acquisition hardware 110. Various acquisition control processes are applied to the acquired waveforms in accordance with various control variables 120 provided by the user via a user interface 115.

Thereafter, various results data are provided to, and thereafter output from a preprocessing system 125 and are in turn acted upon in various post processing functions 130 employing user defined control variables, resulting in processed data (Results data) 135. The post-processed data is then exported and/or imported at 140 as necessary for further processing by the system 145. After processing has been completed, the various processed data is converted for display at 150 on a display device 155.

The internal variables, what can be called “control variables” are a very common and central aspect of any instrument control software. The instrument (oscilloscope or related instrument) has a “state” at any moment in time for example a certain number of components are configured and the processing components each have their state (e.g. the FFT component may have selected a certain “window”, and a timing parameter a certain threshold or hysteresis). If the instrument is to ever be restored to that state, there needs be a means to store or record this overall state.

At any one time, the operator configures the instrument to perform the measuring task at hand by selecting appropriate value or setting for each of many hundred operating properties, that govern, to name only a few for example, the speed of signal capture, the number of measurement points, the sensitivity of input circuits, the type and quality of signal enhancement procedures applied in real time, the style of display of data, the parameters to be evaluated on the captured signals in real time. Each of these properties is embodied in a software entity that we name a Cvar (control variable). The set of current values of all Cvars in the instrument constitutes the control state of the instrument. You use the Cvars to control the state of the scope: the timebase, the vertical channel sensitivity, the trigger conditions, the Math and Parameter settings, the display landscapes, and tens and hundreds of other details.

Operators using the instrument need efficient means for manipulating and viewing the current values and the sets of possible values of Cvars. Manipulators include physical buttons and knobs on the instrument's front panel, virtual buttons and knobs on the instrument's screen, and Remote or Automation commands issued by computer programs that run on separate computers connected to the instrument over a network. Operators also need efficient means for saving entire sets of Cvars in the form of computer files, for the purpose of repeating the same type of measurements at different times and/or in different places. This allows the instrument to remember the settings for the user. The user can also store any number of ‘setups’ that the user can recall at a later date. These setup files can even be exchanged between different scope models via email. Each different model will try to accept the settings from a different model, and adapt them the best it can to approximate the state saved on the other instrument.

At any one time, each Cvar's value must be constrained to remain within a well-defined set or range of values, appropriate and optimal for the operation of the instrument. Such constraints stem from several considerations, for example: 1. For Cvars controlling the physical state of the instrument's hardware, the constraints correspond to physical limits of that hardware and/or what is deemed by the designers of instrument as reasonable, or perhaps optimal use of that hardware; in some cases the limits must be imposed in order to prevent the physical damage to the hardware; 2. For Cvars controlling the signal processing and modes of display of data on the instrument's screen—as graphical traces, surfaces, maps and other images, and as tables of numerical values, these constraints reflect the capabilities of the mathematical software and of the graphics software and hardware built into the instrument; 3. For Cvars controlling the instrument's operation for saving and archiving data and communicating the data over computer networks, these constraints again match the capabilities of the built-in software and hardware.

Overall, such constraints serve to guide the operator in selecting the optimal settings of the instrument, and to prevent him from inadvertently selecting less useful or dangerous combinations of settings. In many cases, constraints currently applicable to any given Cvar depend on, and change with, settings of other closely related Cvars.

For example, the range of acceptable values for Vertical Offset is different for each setting (value) of Vertical Scale, and the instrument software constructed according to this invention will apply the appropriate constraints between these Cvars, whenever the operator changes these settings. This feature frees the operator from of thinking about the instrument's constraints, and lets him fully concentrate on his task of performing the measurements. A user can obtain the range of a Cvar by querying the Cvar's property Range.

Commands to change some or all Cvar values may arrive in any arbitrary order from several types of manipulators, as explained above. It is of utmost importance that the control state of the instrument, resulting from a series of such commands, should remain independent of the order in which these commands were received by the instrument's software. Software constructed according to this invention satisfies this requirement.

A Cvar is a variable inside the computer program that is embedded in the instrument and that governs the operation of the instrument's hardware and software. However, a Cvar is not a simple variable, but an instance of a class, as understood in modern computer programming languages such as C++. This lets the designers of the instrument software to confer to a Cvar a number of useful features, needed in instruments employing modem electronic hardware and computer software. Cvars have an allowed range of values, which may change dynamically, depending on states of other Cvars. Cvars have a memory of value requested by the user. They have memory of value adapted to conform to the current range of allowed values and means for attaching and detaching addresses of other software objects that need to be notified when the value, or range, or another similar property of the Cvar changes. The Cvars have memory of attributes such as “read only” or “hidden” (etc.) to affect the users interaction with it.

The Cvars have a requested value. This is the value most recently requested by the operator of the instrument. In addition to the requested value, cvars have an adapted value. This is the currently applicable value. Further, the cvars have a used value. This is the currently applied value. The used value is usually same as the adapted value, but the used value may temporarily be different from the adapted value, such as when the software or hardware is busy carrying out an operation and not yet ready to apply a new Adapted Value. The Cvars also have a default value. This is the value to which the Cvar returns on command. The type of the Cvar's values may be one of but not limited to: A numeric value of type ‘double’ or ‘real’ with a physical unit, e.g. 0.125 V, A numeric value of type ‘double’, constrained to follow a pattern such as 1,2,5,10,20,50, . . . , a numeric value of type ‘integer’, e.g. 10000 points, one value from an enumeration of several named states, e.g. “AC”, a numeric value encoding a color in a graphics system, text string, e.g. a name of a computer file, a logical 2-state variable (No/Yes, Off/On), ‘Action’ type which embodies a request from the operator to perform some action.

The nature of the range of allowed values depends on the type of the Cvar's value. Thus, the range for a Cvar Double and CvarInt (real and integer values, respectively) is defined by the minimum and the maximum, and the grain (the smallest allowed increment, which may also be thought of as precision or resolution). The range for a CvarEnum is defined by the explicit enumeration (the list) of allowed text strings or keywords. For example, the list “AC”, “DC”, “GND” enumerates three possible states of a CvarEnum that controls the input coupling of one of acquisition channels.

Cvars have boolean (or logical) flags that characterize the state or the intended use of the Cvar, such as read-only (which cannot be modified by the user), hidden (temporarily or permanently hidden from the user if the Graphical interface or GUI), etc. These flags can be modified only by the instrument software via Cvar's C++ interface, normally by the owning CvarBag. They can be read via Automation property ILecCvar::Flags. State of several flags can also be read with specific ILecCvar methods.

Cvar Flags name property value purpose all −1 all bits none 0 no bits (defaults) readonly IsReadOnly 1 Cvar is readonly (C++ clients can use ‘force’ version of SetRequestedValue to bypass) hidden IsHidden 2 Cvar is hidden (no widget desired in GUI) wrap 4 for CvarEnum only: when in- cremented, wraps max to min and vv. lateUpdate 8 Cvar will ask the Bag to SetRequestedValue() before responding to GetAdapted Value() guiOnly IsGuiOnly 16 Cvar will be displayed in the GUI only, never ‘exported’ in vbs format for example fineGrain- 32 for CvarLockstep only: fine grain Allowed increment allowed nonvolatile 64 store in Nvl script, don't store in Panel script reversedDir 128 Increment() decreases the value instead of increasing There are 12 Cvar types listed in the table below.

The 12 Cvar Types Type Interface Purpose Note CvarBool ILecCvarBool Boolean property User toggles CvarColor ILecCvarColor Color Cvar- ILecCvarDouble Double value Double Cvar- ILecCvarDouble Double value E.g. 1, 2, 5, 10, 20, Double- Lockstep locked to discrete . . . Lockstep steps Cvar- ILecCvarEnum List of named Value can be Enum values disabled, can have attachments Cvar- ILecCvarImage Image E.g. for previews in Image a dialog CvarInt ILecCvarInt Integer value 32 bit signed integer Cvar- ILecCvarLatch Boolean action User sets, Latch property application clears Cvar- ILecCvarAction Boolean action User requests Action property immediate action Cvar ILecCvar Contains an IDispatch* in a Object Object Variant CvarRe- ILecCvarRegister Image of a Has bit manipulation gister exit hardware register, methods up to 32-bit Cvar- ILecCvarString Character string E.g. file name String

One example of a Cvar type is Cvar Double. This Cvar provides access to a double with a range and a grain. The range (min and max) limits the adapted value. The grain has multiple meanings depending on it's sign (by convention, a positive grain is taken as an absolute value, while a negative grain is interpreted to mean the corresponding number of significant digits). Another example of a Cvar is the Cvar Double Lock step. This Cvar provides logarithmic incrementing for a range of strictly positive values. Adapted values are locked to steps defined by the lock step argument, for example 1, 2, 5, 10, . . . The Initialize method requires a strictly positive range (0.0<min<default Val<max) and one of enumerated lockstep series.

Cvars may contain Help text that may be displayed to explain to the operator of the instrument the purpose and use of the Cvar. Cvars have an Automation Interface with methods for changing the state of the Cvar, such as set_Value, get_Value, that are available to the operator by means of ‘scripts’. These are executed by controlling programs external to the instrument, and received and processed by the instrument's software.

FIG. 2 graphically represents the Cvars 200. The base Cvar 220 is shown having properties and methods that have meaning to all Cvars. The type-specific Cvars 240, are shown with their properties and methods with internal attributes or member variables whose names start with m_. . . and methods or operations. Cvar 200 is shown with a vector 260 (a list) of Event Sinks 280 or source or targets for event notifications. The type-specific Cvars 240 are sub-classes of the base class Cvar 200 and may themselves have several sub-classes 242 which implement different behaviors behind the same interface.

Cvars have an internal Interface with methods for changing the state of the Cvar, such as set_Name and for attaching or detaching the notification ‘sinks’, that are available only to internal software subsystems. Cvars have a name by which the Cvar is known to internal software subsystems and to the operator using the instrument. Cvars have a list of Cvar Event Sinks or ‘targets’ for notifications of any changes to the Cvar state. This is so that the Event Sinks can react in appropriate manner to these changes. Some possible Event Sinks are the Cvar Bag which ‘owns’ and coordinates a group of Cvars, the Graphical User Interface (GUI) Widgets that display the state of the Cvar to the user, and most importantly, the ‘Engine’ or subsystem whose operation is controlled by the Cvar.

Cvars have software connections to manipulators that let the user change the Cvar's value. Typical classes of manipulators are GUI Widgets, physical devices like pushbuttons and knobs, and Remote Commands which are discussed below. A Cvar also contains a list of Replication Sinks with addresses of dependent Cvars, which are required to replicate the state of the given Cvar. These Sinks receive notifications of selected changes in the notifying Cvar and each proceeds to update it's own state to reflect that of the notifying Cvar.

Another embodiment according to this invention is a Cvar Bag or a Collection of Cvars. The Cvar Bag has a list of contained Cvars. CvarBags are collections of Cvars belong to various subsystems and impose required constraints on Cvar's type and range of values (which may be changing dynamically). The Cvar bag initializes the contained Cvars to sensible default values at the Cvar Bag's creation time. The Cvars contained in the Cvar bag notify the owning Cvar bag of their changes of requested value, range, or attributes. The Cvar bag imposes constraints on Cvar's ranges and values, thus implementing the ‘policies’ that guide the operator in configuring and using the instrument. The Cvar bag has a list of Bag Event Sinks. The Bag Event Sinks are for the purpose of notifications analogous to those described for the Cvars.

FIG. 3 illustrates a CvarBag 300. One Cvar 320 is shown. The Cvar 320 is connected to the CvarBag 300 through a Vector 310 of Cvars and a Vector 330 of Event Sinks. Although only one Cvar 320 is shown, the presence of the vectors imply that there are many Cvars 320. This may indeed be the case. Typically there are 5 to 20 Cvars 320 in one bag.

Another embodiment according to this invention is a Widget. A Widget is a software object that is a means of displaying the state of a Cvar to the operator, or a means of manipulating the value of a Cvar, or both at the same time. A Widget is a View or Manipulator of Cvar. It displays to the user the current value of the Cvar and lets the operator modify the Cvar in some way (touchscreen, mouse interaction, keypad, etc). The typical display Widgets are software objects that control the colored lights (LEDs) on the instrument's panel or on attached probes, and or control various icons on the instrument's screen. Typical manipulator Widgets are software objects that are connected to the instrument panel knobs and buttons, to the touch screen software, or to the pointing device, e.g. mouse, software, or to software controlling the instrument's attached probes which may carry pushbuttons.

A Widget may also be in the ‘both’ category. These Widgets are the on-screen graphic representations of menus, dialogs, buttons, virtual keypads and keyboards, clickable tree-views and the like. By extension, a Remote control widget is the software handler object that ‘understands’ remote command strings sent by the operator over a computer network to the instruments. The handler translates these commands and related queries into ‘set’ and ‘get’ methods on the corresponding Cvars.

A Cvar may at any one time be connected to none, or to one or to several Widgets. Therefore, the operator may manipulate a Cvar by acting on any manipulator Widget attached. The modification of the Cvar's state is always under the direct control of the Cvar's range, which in turn is under direct control of the ‘owning’ Cvar Bag. The modified Cvar state will be displayed by any of the widgets attached. The modified Cvar state will typically affect the appearance of traces and data displayed on the instrument's screen.

FIG. 4 illustrates the concept of Widgets. A Cvar 410 is shown connected to 2 Widgets 420 and 430. In practice there are 0 to N Widgets (perhaps up to 5) and this number varies dynamically, as the user opens and closes dialogs on the screen of the instrument. Some Cvars 410 stay connected permanently, for example to a Front Panel physical knob, via the corresponding software Widget.

To create a widget, the owner of widget, typically a Dialog page, initiates a Widget and attaches a Cvar to it. The Widget turns around and subscribes to notifications of Cvar change events. A Widget is connected to one Cvar, while a Cvar can be connected to any number of Widgets. When a Cvar changes (it's value, range or flag, e.g. becomes read-only), it notifies it's subscribers of the change. Upon notification the Widget updates it's display of Cvar's value (if value changed), makes itself invisible (if Cvar became hidden), etc. When the instrument user manipulates the Widget's controls (buttons, textedit boxes, slider handles, color picker, etc), the Widget's message handler interprets the action and sends a message to the Cvar, typically an Increment( ), or SetValue( ) type message. If this in fact changes the state of Cvar (it might not, e.g. when trying to increment the Cvar when it's Adapted value is already at the end of it's range), the Cvar will send the notification to which the Widget will respond as described just above.

To get rid of a widget, the owner of widget detaches the Cvar by sending the Widget DetachCvar( ) message. The Widget turns around and unsubscribes from notifications of Cvar change events.

Widgets are compatible with Cvars as shown by the following table.

Widget types and corresponding Cvar types. Widget type Compatible Cvar types WidgetButton CvarBool, CvarLatch, CvarAction WidgetCheckbox CvarBool, CvarInt, CvarLatch, CvarAction WidgetColorPicker CyarColor, CvarInt WidgetCombobox CvarEnum WidgetComposite CvarDouble, CvarInt WidgetEditText any Cvar WidgetHSlider CvarDouble, CvarEnum, CvarInt WidgetImage CvarImage WidgetKeypad CvarDouble, CvarInt WidgetListbox CvarEnum WidgetProgEdit CvarString WidgetRadioButton CvarEnum WidgetRegister CvarRegister WidgetRichText CvarString WidgetStaticText any Cvar WidgetUpDown CvarDouble, CvarEnum, CvarInt

FIG. 5 shows the relationship of the Cvars and the other components. The two Cvars 510 and 520 belonging to one CvarBag 530. The Cvar bag 530 belongs to an Engine 540 which can be a Processor, a Renderer, a Channel, e.t.c. FIG. 5 also shows the Operator 550-the person who manipulates the Cvars and observes the effect on Display 552. The Display 552 is run by the Engine 540. The Display 540 may be a display of an oscilloscope trace, whose vertical or horizontal extent, or scale, or position, or color, or any of many other attributes the operator 550 wants to modify.

FIG. 6 shows a sequences of events that takes place when the operator turns a knob on a front panel of an instrument (for example those for Vertical Scale or for Horizontal Scale) using the setup described in FIG. 5. In step S10, the operator 550 turns the knob. In step S14 the knob widget 522 increments the Cvar 510. This means that it tells the Cvar 510 to augment or reduce it's requested value by 1 increment for every ‘click’ of the knob—24 clicks per revolution of knob). In step S14 the Cvar 510 constrains it's adapted value to remain within the current range (that is, it will not let the requested value go beyond the current maximum, or below the current minimum). In step S16, the Cvar 510 notifies it's event sinks, which are typically the parent (owning) CvarBag 530 and one or more Widget 524 and the Engine 540, of the adapted value change. In step S18 the CvarBag 530 notifies the Engine 540 that one of it's Cvars 510 has changed.

In step S20 the Engine uses the newly adapted value of the Cvar 510 in subsequent processing and in step S22 notifies it's sinks such as Display 522 that it's data have been changed and may need a redisplay as in step S32. In step S24 the CvarBag 530 also uses the new value of the Cvar 510 to modify the Range of the OtherCvar 520 (that is, it's Max or it's Min). In step S26 the OtherCvar 520, seeing that it's range has changed, modifies—or not, depending on the actual values involved—it's Adapted Value, and in step S28 notifies it's sinks such as Other Widget 526 (for example, an on-screen text area) which in step S28 displays the numeric value of OtherCvar 520. Then in step S30 Cvar 510 also notifies it's own Widget 524 which in turn redisplays the new value of Cvar 510.

FIG. 7 shows in more detail the inner operation of a Cvar, in 2 cases, the setting of a requested value to a cvar and where a CvarBag sets the maximum value of a Cvar. In the first case, where a Widget 524 sets a requested value 710 to a Cvar 510. This may be, for example, where the Widget 524 is a Front Panel numeric keypad, and the operator typed a new numerical value and pressed the Enter key. In step S10, the Cvar 510 sets it's requested value 710 property. In step S20 the Cvar 510 updates it's adapted value 730. In step S30, the Cvar 510 notifies any and all EventSinks 740 of the adapted value 730 change. In step S40 the EventSink usually turns around and gets the new adapted value 730 and uses it. Each kind of Event Sink does so in a way that is appropriate to it's function in the system. For example, a Widget may display the value, an Engine may use the value to steer it's computation, a CvarBag may change a range of another Cvar, e.t.c.

In the second case the CvarBag 530 sets the maximum value of a Cvar 510. This may be done in response to a change of another Cvar's value. In step S50 the Cvar 510 sets it's Range 720. The Maximum value is part of it's Range, most notably in the case of CvarInt and CvarDouble. In step S60 Cvar 510 updates it's adapted value 730. In step S70, Cvar 510 notifies it's EventSink 740. In step S80 the EventSink usually turns around and gets the new adapted value 730 and uses it, in various ways described with the first case.

Operators also need efficient means for saving the entire set of the instrument's Cvars, and for recalling the Cvars for later use into the same, or into another similar instrument. The oscilloscope or related instrument has a “state” at any moment in time. If the instrument is to ever be restored to that state, there needs be a means to store or record this overall state.

This can be done in the form of a computer file. This computer file is called a Panel File or a Setup File. Instruments that are capable of saving and recalling Panel Files make it possible to repeat the same type of measurements at different times and/or in different places. The advantages to users are that the user can repeat standard measurements from day to day, the user can perform rapid and reliable reconfiguration of the instrument to perform different sets of measurements. The user can also perform automated reconfiguration of instruments under the control of a computer, when the instrument is used as a part of automated testing equipment on production floor and the user can enforce uniform measurement standards in laboratory or on the production floor, both within one industrial plant and worldwide across many plants.

Improved models of instruments are constantly being developed and they progressively replace older models in the hands of operators. It is necessary to design the Panel-related instrument software in a way that makes it possible to recall Panel Files from older models into newer models. The advantages to users are that they preserve the investment that went into creation of their standard measurement procedures (manual or automated), as partially embodied in the instrument's Panel files. The present invention aims at solving problems related to saving, restoring and transmitting electronically the instrument control states embodied in Panel files.

The collective state of many Cvars can be recorded as visual basic script. This is because the control variable objects have been endowed with what is called an “automation interface” (discussed above). As a consequence, when the state of the application is recorded (or saved) it is saved in the form of a basic scripting program. This will be true for any application constructed in this architecture, by virtue mostly of the control variable design. As such, within the context of Microsoft Windows operating system in order to start the instrument software in a given “state” the basic script must be launched. Therefore, the instrument can be completely controlled and/or restored by this same scripting mechanism.

The saved Panel files may be recalled from files on the disk into the instrument, with the effect of restoring the instrument state to what it was at the time when the Panel file was saved. The instrument state may be saved to a Panel file named by the user, when the user decides to do so. The instrument state may also may be automatically saved at preset time intervals, or and when the instrument is turned off. The instrument state that was automatically saved when the instrument was turned off will be automatically restored when the instrument is turned on the next time.

The Panel files are modular down to the level of individual Cvar. The individual Cvar is designated in the Panel file by a hierarchical ‘path’ or ‘address’, illustrated by these two examples: “appA.subB.partC1.cvarX1”, “appA.subB.partC2.cvarX1”. Their meaning is: First, we are addressing the Cvar named “cvarX1”, located in the “part C1” of the subsystem “subB” of the application. “appA”. Second, we are addressing another Cvar also named “cvarX1”, but located in the “part C2” of the same subsystem of the same application. The preferred format of the Panel file is human readable text, with one line for each Cvar. However, this does not exclude alternate formats, such as binary, or encrypted, or compressed, provided that the modularity down to the level of individual Cvar is preserved.

The Panel file text constitutes preferably a computer program in an industry standard programming language. This is exemplified but not limited to Visual Basic Script (VBS). However, this does not exclude alternate text formats that constitute a computer program in a proprietary language. Instruments supporting the Panel files contain software methods or routines that upon command automatically generate or write the appropriate Panel file sections. These methods are located in all levels of the hierarchy of subsystems, so that the hierarchical addresses automatically reflect the hierarchy of subsystems.

The instruments supporting the Panel files contain software methods or routines for reading or recalling or loading the Panel Files. These methods are located in all levels of the hierarchy of subsystems, so each subsystem can recognize Cvar items that belong to it according to it's partial address. Therefore, it can route the information towards the target Cvar, while ignoring the Cvars located on other branches of the hierarchy tree.

Panel Files that are also programs in a known scripting language can be used by operators as models for more elaborate programs for automated control of instruments. The order in which the individual Cvars belonging to a given Cvar Bag appear in the Panel File can be changed at will, without affecting the resulting instrument control state. This is the consequence of the fact that each Cvar stores the Requested value and reevaluates the Adapted value whenever it's constraints change. This allows testing procedures to be automated, and test or monitoring to be performed unattended. This also allows permitted values to be found. Once the basic scripting is performed, the range of permitted settings can be queried by basic scripting. Then, the requested value is cached and can be queried. This permits late resolution of inter-variable constraints.

FIG. 8 shows the initialization of Cvars, panel capture and retrieval. The figure shows a hierarchy of high level objects representative of the software. There are many more of them in the real case. An actual real and complete diagram would be both much wider, and deeper (or taller), in number of hierarchy levels, but this figure is used to illustrate the principle. This figure can be compared to FIG. 1. FIG. 8 shows a number of software objects 720, 730 and 740 at different levels. All the software objects 720, 730 and 740 ‘own’ Cvars 750. Consequently, the construction and initialization of Cvars 750 proceeds in hierarchical fashion, starting at the top. The ApplicationKernel 710 here (although in practice there could be additional layers above it) and each software object 720 constructs and initializes the child objects 730, which in turn construct and initialize their own child objects 740, until the individual Cvars 750 are constructed and initialized.

FIG. 9 is a flow chart showing the initialization of Cvars. The flow for capturing the panel file and reloading the panel file is similar, following the same hierarchical paths. In step S910 the ApplicationKernel constructs and initializes the Acquisition object 721. In step S912 the ApplicationKernel constructs and initializes the Preprocessing object 722. In step S914 the ApplicationKernel constructs and initializes the Processing object 721. In step S916 the ApplicationKernel constructs and initializes the Rendering object 724. In step S918 the Acquisition object 721 constructs and initializes the Horizontal object 731. In step S920 the Acquisition object 721 constructs and initializes the Vertical object 732. In step S922 the Acquisition object 721 constructs and initializes the Trigger object 733. In step S924 the vertical object 732 constructs and initializes the channel object 741. In step S926, the Processing object 723 constructs and initializes the processor object 735. In step S928, the Rendering object constructs and initializes the renderer object 736. In step S930, the Renderer object constructs and initializes Cvar 751.

The following is the Visual Basic script of a Panel file. The hierarchical structure is visible in the ‘composite path strings’ found in that file such as these: Set Acquisition=WaveMaster.Acquisition Set C1=Acquisition.C1 C1.VerScale=0.05 C1.VerOffset 0 C1.Coupling=“DC50”

-   -   C1.BandwidthLimit=“2 MHz”     -   C1.ProbeAttenuation=1         In above examples, the main software object, WaveMaster, owns         Acquisition which owns channel C1 which owns Cvars such as         VerScale which is being set to the requested value of 0.05         volts.

FIG. 10 shows the screen for using the invention. A display screen 1000 is shown. The display screen may be controlled by any modem operating system, such as Microsoft Windows. Display shows waveforms 1010. At the bottom of the display 1000, there are tabs 1020 allowing the user to save/recall, save waveform, recall waveform, save setup, recall setup and disk utilities. Here the Save Setup tab 1022 has been chosen. A setup may be saved by typing a name in internal box 1030 and pressing save button 1040. The Instrument Settings may be saved by typing a visual basic file name in Instrument Setting box 1050 and pressing the save now button 1060. The setups and instrument settings may be recalled in a similar way by choosing the Recall Setup tab 1070.

FIG. 11 shows a graphic representation of a Cvar. The Cvar 1110 is shown. The Cvar 1110 contains increment/decrement 1120 or state change. The incrementing/decrementing algorithm that makes sure that the Requested and therefore the adapted value stay within the limits of the Rang. The Cvar also contains memory for Requested value 1140, adapted value 1130 and range limits and granularity 1170. The Adaption algorithm 1150 uses the range limits and granularity 1170 and the requested value 1140 to figure the adapted value 1130. The Adaptation algorithm that makes sure that a Requested value is memorized, and that the resulting Adapted value stays within the limits of the Range. The requested value 1140 can change the requested value 1140. The Cvar also contains Serialization 1160 for persistence purposes. The Serialization algorithm or process, which is responsible for saving the Cvar value to a Panel file and restoring it from the Panel file. The Cvar 1110 has inputs and outputs. FIG. 11 also shows the most important interactions between the Cvar 1110 and it's environment (other software objects discussed elsewhere—the Bag, the Widgets and the Empire). The inputs or commands from Manipulators that may request to increment/decrement the requested value 1172 (with respect to the current adapted value), to set the requested value to a stated new value 1174, and to set the Cvar's requested value to the (internally known) default value 1176. The outputs or queries coming from Event Sinks that seek to obtain the Requested value 1182, the Adapted value 1184, and the Range information 1178. This is not shown in detail, this may be obtained in the form of text string from any type of Cvar, and in numeric or text string form appropriate for each particular Cvar type.

It will thus be seen that the objects set forth above, among those made apparent from the preceding description, are efficiently attained and, because certain changes may be made in carrying out the above method and in the construction(s) set forth without departing from the spirit and scope of the invention, it is intended that all matter contained in the above description and shown in the accompanying drawings shall be interpreted as illustrative and not in a limiting sense.

It is also to be understood that the following claims are intended to cover all of the generic and specific features of the invention herein described and all statements of the scope of the invention which, as a matter of language, might be said to fall therebetween. 

1. A method for saving and restoring an operational settings of a test instrument run by software, comprising the steps of: initiating a saving operation for saving a set of values reflecting settings of, and adjustments to, the test instrument made by a user; determining each of the internal variables belonging to each of a plurality of hierarchical software objects employed in the operation of the test instrument; saving the determined results to a file in a hierarchical structure corresponding to the hierarchical structure of the software objects; recalling the file on a test instrument different from the test instrument from which the internal variables were stored; and setting the operational settings of the different test instrument in accordance with the recalled internal variables.
 2. The method of claim 1 wherein the file is modular so that only a portion of the stored internal variables need be restored at any time.
 3. The method of claim 1 wherein the internal variables are designated in the file by a hierarchical path.
 4. The method of claim 1 wherein the internal variables may be modified by a change in any of the controls of the test instrument.
 5. The method of claim 1 wherein the internal variables are modified to conform to any requirements of the different test instrument.
 6. The method of claim 1 wherein the file constitutes a computer program.
 7. The method of claim 6 wherein the computer program is an industry standard programming language.
 8. The method of claim 7 wherein the industry standard programming language is Visual Basic Script.
 9. An apparatus for saving and restoring operational settings of a test instrument run by software, comprising: means for initiating a saving operation for saving a set of values reflecting settings of, and adjustments to, the test instrument made by a user; means for determining each of the internal variables belonging to each of a plurality of hierarchical software objects employed in the operation of the test instrument; means for saving the determined results to a file in a hierarchical structure corresponding to the hierarchical structure of the software objects; recalling the file on a test instrument different from the test instrument from which the internal variables were stored; and means for setting the operational settings of the different test instrument in accordance with the recalled internal variables.
 10. The apparatus of claim 9 wherein the file is modular so that only a portion of the stored internal variables need be restored at any time.
 11. The apparatus of claim 9 wherein the internal variables are designated in the file by a hierarchical path.
 12. The apparatus of claim 9 wherein the internal variables may be modified by a change in any of the controls of the test instrument.
 13. The apparatus of claim 9 wherein the internal variables are modified to conform to any requirements of the different test instrument.
 14. The apparatus of claim 9 wherein the file constitutes a computer program.
 15. The apparatus of claim 14 wherein the computer program is an industry standard programming language.
 16. The apparatus of claim 15 wherein the industry standard programming language is Visual Basic Script.
 17. A method for saving and restoring an operational settings of a test instrument run by software, comprising the steps of: initiating a saving operation for saving a set of values reflecting settings of, and adjustments to, the test instrument made by a user; determining each of the internal variables belonging to each of a plurality of hierarchical software objects employed in the operation of the test instrument; saving the determined results to a file in a hierarchical structure corresponding to the hierarchical structure of the software objects; recalling the file on a test instrument different from the test instrument from which the internal variables were stored; and modifying the internal variables as determined by the different test instrument; setting the operational settings of the different test instrument in accordance with the recalled, modified internal variables. 